Hello. I have developed a script which is intended to give myself as the Exchange admin full access to a mailbox, then open Outlook to that user's profile. Everything is working great, however... I'm assuming it's a replication issue where most often it takes 2 or 3 minutes before Outlook will open to the new profile without prompting me for credentials (and not accepting them when typed in). My questions first, then I'll explain my process:

1.) I've read in several places that often replication issues can be resolved by restarting the information store - will that resolve my issue?

A.) If so, what impact or negative issues may arise from arbitrarily restarting the IS just so I can load a user's mailbox faster?

2.) Does anyone know of a way to check and see if the settings have replicated? If so, I could task the script with checking until it occurs, and then attempt to open Outlook to the new profile.

The script is a powershell 3.0, running on any box, but probably a Windows 7 or 8 machine. A PS session is created to the CAS server, and the Exchange configuration is imported. Then, full access permissions are granted via Add-MailboxPermissions cmdlet. The session is closed, and an Outlook .prf file is updated with the user's info. Then, Outlook is started with the /importprf switch and the .prf filename. It is at this point where it usually will not yet recognize that I've been granted full access permissions, and ask for credentials rather than opening the mailbox.

I've done a lot of searching for helpful info, but seem to be coming up short. Any help provided is much appreciated!

EDIT: I've added a section to stop the IS service, then restart it. This seems to have improved the ratio of mailboxes that open considerably. I am still interested in if there are any detrimental side effects of doing this though, and also if there is any way to query the information store to see if the needed info is there. 

• Edited by JosefMH 13 hours 20 minutes ago Update